Skip to content

Conversation

jallisonciq
Copy link

The default DRBG is the one that has the highest priority. The priority
is defined based on the order of the list drbg_cores[] where the highest
priority is given to the last entry by drbg_fill_array.

With this patch the default DRBG is switched from HMAC SHA256 to HMAC
SHA512 to support compliance with SP800-90B and SP800-90C (current
draft).

The user of the crypto API is completely unaffected by the change.

Signed-off-by: Stephan Mueller <[email protected]>
Acked-by: simo Sorce <[email protected]>
Signed-off-by: Herbert Xu <[email protected]>

This changes the default DRBG back to HMAC SHA256 as more processors have hardware acceleration for this algorithm.

Approved by the lab.

Copy link
Collaborator

@PlaidCat PlaidCat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just git commit message comments
This is kinda how i'm used to seeing it when looking at reverts

Revert: crypto: DRBG - switch to HMAC SHA512 DRBG as default DRBG

The default DRBG is the one that has the highest priority. The priority
is defined based on the order of the list drbg_cores[] where the highest
priority is given to the last entry by drbg_fill_array.

With this patch the default DRBG is switched from HMAC SHA256 to HMAC
SHA512 to support compliance with SP800-90B and SP800-90C (current
draft).

The user of the crypto API is completely unaffected by the change.

Signed-off-by: Stephan Mueller <[email protected]>
Acked-by: simo Sorce <[email protected]>
Signed-off-by: Herbert Xu <[email protected]>

Could we maybe do something like this to keep our header?
I don't want to hold this up too much but we haven't really created a standard for this process

Revert: crypto: DRBG - switch to HMAC SHA512 DRBG as default DRBG

JIRA <number>
CIQ Revert
Original Author <email>
Original Commit 9b7b94683a9b9c42a743d591e48b9f51f505dd1f
Revert Reason: This changes the default DRBG back to HMAC SHA256 as more
processors have hardware acceleration for this algorithm.
Approved by the lab.

<original Message>

Signed-off-by: Jeremy Allison <[email protected]>

kinda like how we do the backports
8766d31

JIRA: INTERNAL
Revert Author <[email protected]>
Revert Commit 9b7b946
Revert Reason: This changes the default DRBG back to HMAC SHA256 as more
processors have hardware acceleration for this algorithm.
Approved by the lab.

	The default DRBG is the one that has the highest priority. The priority
	is defined based on the order of the list drbg_cores[] where the highest
	priority is given to the last entry by drbg_fill_array.

	With this patch the default DRBG is switched from HMAC SHA256 to HMAC
	SHA512 to support compliance with SP800-90B and SP800-90C (current
	draft).

	The user of the crypto API is completely unaffected by the change.

	Signed-off-by: Stephan Mueller <[email protected]>
	Acked-by: simo Sorce <[email protected]>
	Signed-off-by: Herbert Xu <[email protected]>

Signed-off-by: Jeremy Allison <[email protected]>
@jallisonciq jallisonciq force-pushed the {jallison}-replace-drbg-with-256 branch from 3a6e1bd to 7b40253 Compare July 15, 2025 22:04
@jallisonciq
Copy link
Author

Updated commit message. JIRA: is marked "internal" as I didn't think we are publishing internal jira ticket numbers.

@PlaidCat
Copy link
Collaborator

We have been, its not public so its not useful to anyone other than us.

Copy link
Collaborator

@PlaidCat PlaidCat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems fine by me, thank you for the updates to the COMMIT message
:shipit:

@jallisonciq jallisonciq merged commit 18bb3b9 into fips-9-compliant/5.14.0-570.25.1.el9_6 Jul 16, 2025
4 checks passed
@jallisonciq jallisonciq deleted the {jallison}-replace-drbg-with-256 branch July 16, 2025 00:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants